permission fix with unit tests fix

Fixed PATCH endpoint to allow specifying only fields to be updated

…as because we were sending response before transaction commit. Fixed the same for milestone template as well and for update endpoints for milestone and milestone template as well.

Made fields in update call to milestone endpoint, optional so that user can specify only sub set of the fields to be updated.

…odel

— Added logic to handle the product as reference for timeline

…estone.

- Should be fixed now

…nes together

— Implemented the functionality by reading the templateId instead of reading the milestones in the request body. This would make things consistent with the way we are handling project and phases.

— Fixed permission logic for milestones

…efore transaction commit which is causing significant extra time for the transaction to complete which in turn causing other operations of the same table to fail because of table locks.

…reate and Update were fixed previously.

…fixed before and update is not using transactions as of now which is a separate issue to fix.

…vice/labels/community-task

- Added connectProjectsUrl config var to test.json, as it's needed for running tests.

… api.

- Added connectProjectsUrl config var to test.json, as it's needed for running tests.

…Date, endDate and duration.

…e and endDate.

…tes of subsequent milestones.

- Fixed bug where the transaction wasn't being included into wrapped queries.

Also, makes one thing, from status and completionDate, optional to mark a milestone complete

Issue #128

…unnecessary calls

…ading the changes in a milestone

- Should be fixed now

…encoded query params

— Should be fixed

… when they are updated via cascaded changes

Removed code to recalculate the order of the milestones for ES indexing, now it should be carrying those changes to the ES via cascaded updates

…f milestone is changed.

…active earlier or later than its scheduled start

…e and endDate so that we can pass them without each other